Update tech-insights workspace to commit 6e6b884 for backstage 1.39.0 on branch release-1.7
#1393
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….39.0` on branch `release-1.7`
github-actions
bot
requested review from
davidfestal,
gashcrumb and
kadel
as code owners
github-actions
bot
added
release-branch-patch
Member
|
/publish |
Contributor
Author
|
Publish workflow has completed with success.
|
christoph-jerolimov
deleted the
workspaces/release-1.7__tech-insights
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update tech-insights workspace at commit backstage/community-plugins@6e6b884 for backstage
1.39.0on branchrelease-1.7.This PR was created automatically.
Click on the following link to see the source diff it introduces: backstage/community-plugins@947c582...6e6b884.
Before merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.
To do so, you can use the
/publishinstruction in a PR review comment.This will start a PR check workflow to: